home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The 640 MEG Shareware Studio 2
/
The 640 Meg Shareware Studio CD-ROM Volume II (Data Express)(1993).ISO
/
door
/
mm20b31.zip
/
!UPGRADE.!!!
< prev
next >
Wrap
Text File
|
1992-11-18
|
15KB
|
222 lines
Upgrading from MarkMail ß29 or earlier to ß31.
Current ß30 SysOps can skip to the paragraph at the end of this file.
UPGRADE INSTRUCTIONS!
This and future MarkMail releases will include a default MARKMAIL.DAT
file. Make sure you DO NOT overwrite your existing MARKMAIL.DAT file.
All of the upgrading that you will need to do will be marked with an
asterisk '*' in column '1' with the exception of the first '*'. That
first * merely signifies a change in the menu to show a location with
a new 'dual purpose', storage of Pointer Files and (soon) QWK packets.
In MarkMail System Manager (MMSM.EXE), choose A) System Configuration,
then choose Paths and File Names.
╔═════════════════════════════════════════════════════════════════════════════╗
║ General Configuration ║
║ ║
║ ║
║ The following fields are locations only. Enter ║
║ the Drive Letter, Path and Trailing Backslash. ║
║ Location of Help & OPT.TXT Files : C:\MM200\HELP\ ║
║ Location of Local .REP Uploads : K:\TEMP\ ║
║ Location of Local .QWK Downloads : K:\TEMP\ ║
* Location of Local PNT/QWK Storage : G:\MM200\STORE\ ║
║ ║
║ ║
║ The following fields, unlike above, require the filenames. ║
║ Enter the Drive, Path and *Filenames* for these fields. ║
║ Name and Location of NEWUSER File : C:\MM200\NEWUSR ║
║ Name and Location of NEWS(g) File : C:\MM200\NEWS ║
║ Name and Location of MENU(g) File : C:\MM200\MM-MENU ║
║ Name and Location of TCAN File : G:\MM200\TCAN ║
║ ║
║ ║
║ This field is a single letter entry so that the MarkMail door ║
║ will know which drive to create the temp work directories on. ║
║ Drive to use for Work Directory : C ║
║ ║
╚═ 08:09:19 ════ 11-18-92 ════════════════════ caps: OFF num: OFF ins: ON ═╝
Then choose Flags and Baud Rates to change new flags.
The UG (Upload and Goodbye) function is now enabled! But for MarkMail
to have this ability it must be flagged as 'Y' as shown below. Also,
the new "short/long logging" toggle must be flagged as 'Y' for Mark-
Mail to log as it always has (1 line to the log per message inserted.
╔═════════════════════════════════════════════════════════════════════════════╗
║ Flags and Baud Rates ║
║ ║
║ This feature allows users to upload a REP packet and logoff. The advantage║
║ is that the message insertion takes place `AFTER' the user has logged off.║
* Allow Users to 'Upload and Goodbye' : Y ║
║ ║
║ This feature allows you to assign file upload credits for REP uploads. If║
║ you assign a number of 2, after 2 REPs the user gets 1 file upload credit.║
║ Number of Rep's for Upload Credit : 0 (0 = No Credit Given) ║
║ ║
║ This feature allows you to reduce the size of your caller logs by logging║
║ a single line of messages inserted/blocked instead of 1 line per message.║
* Write Long Logs for Uploads : Y ║
║ ║
║ This fields allow you to `limit' the size of packets or number of messages║
║ based on the callers baud rate. You can enter default and maximum numbers.║
║ Baud : 300 1200 2400 9600+ ║
║ Default Messages per Conference : 150 150 200 500 ║
║ Default Messages per Packet : 300 600 900 3000 ║
║ Maximum Messages per Conference : 150 150 200 500 ║
║ Maximum Messages per Packet : 300 600 900 3000 ║
║ ║
║ ║
╚═ 08:09:33 ════ 11-18-92 ════════════════════ caps: OFF num: OFF ins: ON ═╝
Then choose Conference Config (Individual or By Range is up to you).
Two new conference flags give MarkMail greater flexibility! But use
with discretion. The more significant of the new R and A flags is A.
The 'A' flag will allow users to upload mail where the 'From:" field
is *not* their name. This allows networks supporting aliases to give
MarkMail users the ability to enter offline 'aliased mail'.
The 'R' flag should be more widely used if your network supports R/O
mail. Flagging a networked conference with the 'R' flag will allow
SysOps to download R/O mail even if the R/O message is not to them.
Not having the 'R' flag in a conference is advantageous in a 'Regional
type of conference where you only want a R/O message to go to one of
your nodes. While this is an advantage, we do not endorse the use of
private mail nor are suggesting it's use.
╔═════════════════════════════════════════════════════════════════════════════╗
║ Conference Config, Individual Page 1 of 18║
║ Ignore (E)cho Flag - (F)orce Conference - (N)ew User Conference ║
║ Ignore (P)cboard Registration - Allow (Y)our Mail - Check (D)upes ║
* Allow (A)lias - Send (R)/O Mail to Net-Sysops ║
║ ║
║ Num Conference Net Flags Days Num Conference Net Flags Days ║
║ ──── ────────────── ───── ───── ──── ───── ────────────── ───── ───── ──── ║
║ 0 Main Board LO YDR 60 14 Printers IN YDR 60 ║
║ 1 Technical IN YDR 60 15 MAC IN YDR 60 ║
║ 2 Batch IN YDR 60 16 SpitFire IN YDR 60 ║
║ 3 Compression IN YDR 60 17 Moderate IN YDR 60 ║
║ 4 Multitask IN YDR 60 18 Amiga IN YDR 60 ║
║ 5 LAN IN YDR 60 19 Comm IN YDR 60 ║
║ 6 Qedit IN YDR 60 20 SysOp IN YDR 60 ║
║ 7 WordProc IN YDR 60 21 BBS-Door IN YDR 60 ║
║ 8 DeskTopPub IN YDR 60 22 Ads IN YDR 60 ║
║ 9 Video IN YDR 60 23 NetChat IN YDR 60 ║
║ 10 Database IN YDR 60 24 CorelDraw IN YDR 60 ║
║ 11 Programmer IN YDR 60 25 NetAdmin IN YDR 60 ║
║ 12 IN_Reserved IN YDR 60 26 ProComm IN YDR 60 ║
║ 13 Hardware IN YDR 60 27 MM-Alpha IN YDR 60 ║
║ ║
║ Use Arrow Keys, Pg-Up, Pg-Dn - F2 to Change Network - ESC to Exit ║
╚═ 08:09:33 ════ 11-18-92 ════════════════════ caps: OFF num: OFF ins: ON ═╝
Then choose User File/TPA Maintenance to adjust any users with Net Status.
For users (whether Net SysOps or users) that you want to store pointer
files for, flag the "Store Users Pointers:" field with a 'Y' as shown
below. Pointer files will be stored in the directory which you have
specified in the Paths and File Names section. Then, to grant Net Status
in specific networks only, press F2 while in the Net-Mail Status field
(if it is flagged with a 'Y'. Go to the 'next' screen below...
╔═════════════════════════════════════════════════════════════════════════════╗
║ Edit MarkMail User Record Record 1 of 8║
║ ║
║ Name : CLIFF WATKINS ║
║ Security Level : 255
║ Been in MarkMail : Yes Alt-F Find User Name ▓
║ Alt-S Search for Text ▓
* Net-Mail Status : Y Alt-L Locate Security Level ▓
║ Offline Packets : N Alt-R Repeat Last Search ▓
║ Receive Own Mail : N Alt-J Jump to Record Number ▓
║ Expert Mode : N Alt-T Jump to Top Record ▓
* Store Users Pointers: Y Alt-B Jump to Bottom Record ▓
║ Alt-P Print Current Record ▓
║ Transfer Protocol : Z ▓
║ Max Messages/Conf : 400 ▓
║ Max Messages/Total : 1500 ▓
║ Max Qwk Size in K : 0 0=Unlimited ▓
║ ▓
║ Date of Last QWK : 01/05/92 Number of QWK's : 119 ▓
║ Time of Last QWK : 13:08 Number of REP's : 106 ▓
║ ▓
║ Press F2 to rotate between different views
║ ║
║ ESC=Exit PgDn=Forw PgUp=Back Ctrl-PgDn=Forw20 Ctrl-PgUp=Back20 ║
╚═ 08:09:33 ════ 11-18-92 ════════════════════ caps: OFF num: OFF ins: ON ═╝
If you pressed F2 while in the "Net-Mail Status: Y" field, this is the
screen you will see next. Simply flag Y or N to the networks you want
this Net User to have Net Status in. It's that easy. Since MarkMail's
previous method of Net Status was 'global' there should be all 'Y's'
in these fields. Just type 'N' where you do not want a user to have Net
Status and any network flagged 'N' will not be viewable or selectable
while that user is in the MarkMail door, *regardless* of wether or not
the user is registered in them in PCBoard. This will allow you to give
conference access to a Net Status user in PCBoard while not giving him
or her Net Status in that conference in MarkMail.
╔═════════════════════════════════════════════════════════════════════════════╗
║ Edit MarkMail User Record Record 1 of 8║
║ ║
║ Name : CLIFF WATKINS ║
║ Security Level : 255
║ ▓
║ Network Name Code Reg ▓
║ ────────────── ────── ───── ▓
* Local LO N ▓
* Intelec IN Y ▓
* SF_Net SF Y ▓
* BizNet BZ Y ▓
* ThrobNet TH Y ▓
║ ▓
║ ║
╚═ 08:09:33 ════ 11-18-92 ════════════════════ caps: OFF num: OFF ins: ON ═╝
H A V E Y O U U P G R A D E D Y O U R K E Y F I L E Y E T ?
If you have not yet upgraded your MARKMAIL.SYS registration key file,
DO NOT UPGRADE to this version until you do!! Your door will act as an
"unregistered version" unless you follow the instructions below...
If you ordered the door anytime during '92 or ordered it directly from
Intelec Online, you've already got the new style registration key.
As stated many times in the several MarkMail support conferences, and as
mentioned in each release since I took over from Mark, this beta version
#30 NO LONGER USES the old style MARKMAIL.SYS key file. If you have not
yet upgraded your key file, you **MUST** do so before upgrading to this
beta #30! Again, ß28 was the LAST beta using "both the old and new" SYS
files. So call Intelec Online and update your SYS file to the new format
as soon as possible. Use our UPDATE door to do this. Simply upload your
MARKMAIL.SYS file into the door, it will update it automatically and it
will go into Zmodem D/L mode when complete, only a couple of seconds....
Do not wait to be validated, it's available on the very first call and I
will use that door's log to perform security level upgrades.
That's it... this is the extent of any upgrade required for going from
MarkMail ß29 or earlier to ß31. I hope you enjoy all the enhancements
and greater flexibility that this version will give you!
< For those currently running ß30 >
For those of you upgrading from ß30 to ß31, the executables are drop-
in replacements. Make sure that you > do not < overwrite your existing
MARKMAIL.DAT file with the one included with the distribution file. We
have also added support for additional help files (OPTnn.TXT) that are
included in the MMHELP.ZIP file and should go in the same directory as
your current help files as defined in MMSM. Run MMSM.EXE and exit/save
so that your MARKMAIL.DAT file is upgraded. This *MUST* be done if you
are upgrading from *ANY* previous beta version of MarkMail v2.00.
Thank you!
Cliff Watkins
MarkMail Support